Add configurable ReleaseFiles parameter for release-triggering file patterns #95
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release-triggering file patterns (e.g.,
action.yml,src/**) were hardcoded in the workflowpathsfilter. Users had no way to control which file changes should warrant a release.Changes
action.yml: NewReleaseFilesinput — comma-separated glob patterns, default empty (opt-in, fully backward compatible)src/main.ps1: ReadReleaseFilesfrom config file or input, match PR changed files viagh pr diff --name-onlyagainst patterns using-like, skip release if nothing matchesREADME.md: DocumentReleaseFilesin settings table and config file exampleUsage
As an action input:
Or in
.github/auto-release.yml:When
ReleaseFilesis empty (default), all file changes trigger releases — no behavior change for existing users.Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.